After a little cleanup commit, I did more tests today (ADIOS2, HDF5) and the particles and fields look great, as well as particles transitioning between patches.

I am double-checking with @RevathiJambunathan that the back-transformed diagnostics is still working and after that I think it can go in :)

Thanks for this PR!

I tested this for Back Transformed diagnostics and get an error:

STEP 64 starts ...
STEP 64 ends. TIME = 6.814271277e-13 DT = 1.064729887e-14
Walltime = 19.13449687 s; This step = 0.184028665 s; Avg. per step = 0.2989765135 s
terminate called after throwing an instance of 'std::runtime_error'
  what():  [Series] Detected illegal access to iteration that has been closed previously.
SIGABRT
/usr/bin/addr2line: DWARF error: could not find variable specification at offset 240e1
/usr/bin/addr2line: DWARF error: could not find variable specification at offset 240e1
See Backtrace.0.0 file for details
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI COMMUNICATOR 3 DUP FROM 0
with errorcode 6.

Here is the input file

inputs_3d_slice_reformatted.txt

Thanks for this PR!

I tested this for Back Transformed diagnostics and get an error:

STEP 64 starts ...
STEP 64 ends. TIME = 6.814271277e-13 DT = 1.064729887e-14
Walltime = 19.13449687 s; This step = 0.184028665 s; Avg. per step = 0.2989765135 s
terminate called after throwing an instance of 'std::runtime_error'
  what():  [Series] Detected illegal access to iteration that has been closed previously.
SIGABRT
/usr/bin/addr2line: DWARF error: could not find variable specification at offset 240e1
/usr/bin/addr2line: DWARF error: could not find variable specification at offset 240e1
See Backtrace.0.0 file for details
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI COMMUNICATOR 3 DUP FROM 0
with errorcode 6.

Here is the input file

inputs_3d_slice_reformatted.txt

Thanks I will take a look later today

The crash is likely due to additional patch parts that should remain in #1909 for the transition to group & variable based I/O options. I'll clean them out and re-test.

The crash is likely due to additional patch parts that should remain in #1909 for the transition to group & variable based I/O options. I'll clean them out and re-test.

Would be great see why 1909 is not passing the CI.

I removed the un-related streaming API changes from this PR.
I performed @RevathiJambunathan's test again and BTD works again :)

Let's also add BTD with openPMD to CI in a PR.